Method and system of alert notification

ABSTRACT

Method and system for alert notification is provided. A Simple Object Access Protocol (SOAP) based alert notification is sent from one or more agents, and the SOAP based alert notification(s) is received at a manager.

REFERENCE TO RELATED APPLICATIONS

The present disclosure is based on and claims the benefit of ProvisionalApplications 60/460,208 filed Apr. 4, 2003, entitled “Web Services BasedDiscovery of Remote Agents”, 60/460,467 filed Apr. 4, 2003, entitled“SOAP Based Alert Notifications for System Management”, and 60/460,258filed Apr. 4, 2003, entitled “Web Services Based Management andConfiguration of Remote Agents”, the entire contents of which are hereinincorporated by reference.

BACKGROUND

1. Technical Field

The present disclosure relates generally systems management and, moreparticularly, to a method and system of alert notification.

2. Description of the Related Art

Systems management involves the supervision of information technology inan enterprise. System management tools may include two primary elements,agents and managers. The agents are the entities that provide aninterface to a device that needs to be managed, such as a server,router, bridge, hub, printer, etc. The device, such as a server, cancontain a series of managed objects, such as hardware, configurationparameters, performance statistics, etc. which can all be managed by theagents. The manager can be a user interface to enable a user, such as anetwork administrator to perform management functions, such asconstantly viewing and changing the configuration and status of remoteagents.

It is useful if users, such as network administrators are able todiscover agents and remotely manage them from a central managementconsole through a web based service. In addition, it is useful ifmanagers are able to accurately receive alert notifications to alertthem of changes that can occur on an agent system. In globallydistributed networks, there is a very high likelihood of a firewall,proxy server, and/or virtual private network (“VPNs”) between the agentnodes and the management console. It is useful if a manager is able todiscover, manage and configure a wide variety of agents through a singlemanagement console across the firewall, proxy server, and/or VPNs.

Simple Network Management Protocol (“SNMP”) is a standard designed tohelp managers remotely manage devices, such as servers, printers,routers, etc. However, in the presence of a firewall, proxy server, orVPN, SNMP can prove to be unreliable.

Accordingly, it would be beneficial to provide a reliable and effectiveway to ensure that remote agents are able to send alerts to the eventconsole, and are effectively managed and configured.

SUMMARY

A method of alert notification, according to an embodiment of thepresent disclosure, includes sending a Simple Object Access Protocol(SOAP) based alert notification from one or more agents, and receivingthe SOAP based alert notifications at a manager.

A system of alert notification, according to an embodiment of thepresent disclosure Includes at least one agent for sending a SOAP basedalert notification, and at least one manager for receiving the SOAPbased alert notification.

A computer storage medium including computer executable code for alertnotification, according to an embodiment of the present disclosure,includes code for sending a SOAP based alert notification, and code forreceiving the SOAP based alert notification.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete appreciation of the present disclosure and many of theattendant advantages thereof will be readily obtained as the samebecomes better understood by reference to the following detaileddescription when considered in connection with the accompanyingdrawings, wherein:

FIG. 1 shows a block diagram of an exemplary computer system capable ofimplementing the method and system of the present disclosure;

FIG. 2 shows a system for agent management, according to an embodimentof the present disclosure;

FIG. 3 shows a schematic diagram illustrating the discoveryarchitecture, according to an embodiment of the present disclosure; FIG.4 shows a flow chart illustrating the sequence of execution of all theoperations on a specified target during the discovery process, accordingto an embodiment of the present disclosure;

FIG. 5 shows a block diagram illustrating how the Agent Metadata Serviceprovides metadata to clients; according to an embodiment of the presentdisclosure; FIG. 6 shows a graphical user interface allowing the user tochoose between the two different discovery modes, according to anembodiment of the present disclosure;

FIG. 7 shows the second step of the discovery process, in which agraphical user interface is provided allowing the user to select andenter profile information, according to an embodiment of the presentdisclosure;

FIG. 8 shows a graphical user interface allowing a user to perform thethird step of entering agent host information, according to anembodiment of the present disclosure;

FIG. 9 shows a graphical user interface allowing the user to input proxydetails for an agent or manager, according to an embodiment of thepresent disclosure;

FIG. 10 shows a graphical user interface allowing the user to inputconnection details for an agent or manager, according to an embodimentof the present disclosure;

FIG. 11 shows a graphical user interface for verifying securitycredentials, according to an embodiment of the present disclosure; and

FIG. 12 shows a graphical user interface used for presenting a list ofdiscovered agents to a user, according to an embodiment of the presentdisclosure.

DETAILED DESCRIPTION

The present disclosure provides tools (in the form of methodologies,apparatuses, and systems) for alert notification. The tools may beembodied in one or more computer programs stored on a computer readablemedium or program storage device and/or transmitted via a computernetwork or other transmission medium.

The following exemplary embodiments are set forth to aid in anunderstanding of the subject matter of this disclosure, but are notintended, and should not be construed, to limit in any way the claimswhich follow thereafter. Therefore, while specific terminology isemployed for the sake of clarity in describing some exemplaryembodiments, the present disclosure is not intended to be limited to thespecific terminology so selected, and it is to be understood that eachspecific element includes all technical equivalents which operate in asimilar manner.

FIG. 1 shows an example of a computer system 100 which may implement themethod and system of the present disclosure. The system and method ofthe present disclosure may be implemented in the form of a softwareapplication running on a computer system, for example, a mainframe,personal computer (PC), handheld computer, server, etc. The softwareapplication may be stored on a recording media locally accessible by thecomputer system, for example, floppy disk, compact disk, hard disk,etc., or may be remote from the computer system and accessible via ahard wired or wireless connection to a network, for example, a localarea network, or the Internet.

The computer system 100 can include a central processing unit (CPU) 102,program and data storage devices 104, a printer interface 106, a displayunit 108, a (LAN) local area network data transmission controller 110, aLAN interface 112, a network controller 114, an internal bus 116, andone or more input devices 118 (for example, a keyboard, mouse etc.). Asshown, the system 100 may be connected to a database 120, via a link122.

According to an embodiment of the present disclosure, a managementapplication (i.e., a manager) can be installed in three components: anagent, which can reside on the same system as the application server; amanager, which can be fully integrated with the management applicationor can stand alone, and a console, which can provide a user interface.System(s) as referred to herein may include(s) individual computers,servers, computing resources, networks or combinations thereof, etc.Users of the management application can include, application serveradministrators, system administrators, performance managers, andapplication server developers, etc. Since the agents and managers may bein a distributed environment, they may be separated by firewalls, proxyservers, and/or VPNs, etc, where SNMP is not a practical communicationprotocol. According to an embodiment of the present disclosure, a SimpleObject Access Protocol (SOAP) is utilized. SOAP is a stateless, one-waymessage exchange system which can also be utilized to performrequest/response, request/multiple responses, etc. in a distributedenvironment.

Discovery is a process of creating a manager side representation of theagent side schema and can touch every layer of the managementapplication. A successful discovery process may be implemented for theadministration, configuration and overall successful functioning of themanagement application. According to an embodiment of the presentdisclosure, web based agent services can discover any type of remoteagent through a single management console, even through firewalls, proxyservers, and/or VPNs, etc.

After remote agents are discovered by the management console, a user,such as a system administrator, may constantly view and change theconfiguration and status of remote agents. Therefore, it is useful ifagents are able to be configured to run across firewalls, proxy servers,and/or VPNs, etc. According to an embodiment of the present disclosure,a single management console can manage web based remote agents and canbe configured to run across firewalls, proxy servers, and/or VPNs.

An agent can have a layout and hierarchy of various types, with eachinstance representing the various facets of the managed resources, bothindividual and collective. The discovery process can identify thisschema, translate it into a manager side representation compatible witha manager repository, and create the representation in the managerrepository, making the data available for various other applications viathe repository. Discovery can also include both registering the managerwith the agent as a recipient of alert notifications as and when theyare raised by the agent and initializing performance data collection forthe agent and its objects.

A more detailed description of a system for agent management andconfiguration of remote agents, according to an embodiment of thepresent disclosure, will be described with reference to FIG. 2. Eachagent 212 is a software component capable of monitoring managed objectsand reporting their status to a J2EE manager 207 through a communicationinfrastructure 210. An example of an agent may include, for example, 100managed objects and can handle XML/character data information.

Examples of managed objects are the devices, systems, and/or anyhardware or software that require some form of monitoring andmanagement. A managed object can be defined in terms of the attributesit possesses, operations that may be performed on it, and itsrelationship with other managed objects. According to an embodiment ofthe present disclosure, a managed object can be a one-to-one mapping tothe manageable entities within an application server and its components.The managed objects are described in further detail below.

A Service Manager User Interface 202 may, for example, be similar to a“Windows”Service manager and is used to discover and configure theagent, view the status of the managed objects and/or launch reports. TheService Manager User Interface 202 can allow a user to start, stop, andrecycle services including, for example, the following manager services:J2EE manager 207, J2EE data collector 208, and J2EE reporter 209 throughcommunication structure 206. J2EE manager 207 can register itself withall discovered agents and can log agent behavior for life cyclemanagement. J2EE manager 207 can have a scheduler to enable timed eventsand can send out email notifications due to alerts.

A user can have the option to collect data and can set a pre-definedcollection frequency. J2EE data collector 208 can collect this data forthe agents and their objects via agent infrastructure 211. A user canlaunch reports generated by the J2EE reporter 209 through the ServiceManager User Interface 202. J2EE manager 207 and agents 212 cancommunicate using SOAP through communication infrastructure 210 and theJ2EE manager 207 can communicate with the user interface 202 using HTTPthrough communication infrastructure 206.

The Service Manager User Interface 202 can include a management console203, a management portal 204 and/or a graphical utility 205. Themanagement console 203 can be a java based manager component thatdisplays an event, such as an unsolicited alert notification from amanager or agent indicating, for example, that one of the followingconditions may have occurred: a threshold limit was exceeded, thenetwork topology changed, an informational message or error occurred,and/or an application alert occurred, etc. There is no set limit to thenumber of users that can access the management console 203. Themanagement console 203 can be used to create, update and deletemonitored objects. A command line utility can be provided to allow auser to perform all user interface functions from the command line. Themanagement console 203 can be a plug in or can be launched via a rightclick menu. Agents 212 can be configured through the management console203 and users can configure the monitoring interval for each object. Thecurrent status and value for each selected object can be providedthrough the management console 203. The management console 203 can alsoallow a user to enter and edit threshold values, such as, for example,“Warning”, “Major”, and “Critical”. The threshold values can pertain toa threshold level associated with alert notifications. Alertnotifications that are of a lower priority value than the thresholdvalue, for example, may not be displayed on the management console 203.The management console 203 can list all registered managers. Accordingto an embodiment of the present disclosure, the type of information thatis handled can be XML/character data and the maximum size of theinformation handled can be 1K/request.

Management portal 204 can provide a web based information managementsystem that provides a single access point for users to shareinformation. For example, a system administrator can use the managementportal 204 to access the management console 203 that can be used tomanage and configure one or more remote agents.

The graphical utility 205 is a manager component that enables a user,such as a system administrator, to configure, browse, and/or edit anyagent configuration. The utility can provide an interface to add,remove, and modify objects in the configuration.

A common object repository 201 provides other applications with datathat is common to all.

Discovery may utilize a series of services/modules from the agent andthe user interface that assist in the discovery process. FIG. 3 is aschematic diagram illustrating the discovery architecture, according toan embodiment of the present disclosure. The diagram is divided intothree parts, where each part represents a layer of the product. Thegraphical user interface (“GUI”) 205 is used to initiate the discoveryprocess via a discovery wizard 312. The actual discovery is launched bya manager 207 against an agent 212.

The Agent Metadata Service 304, Agent Managed Object Query Service 305,and Agent Trap Registration Service 306 are examples of services runningon an agent 212. The Agent Metadata Service 304 supports queries toretrieve metadata information residing on the agent 212. The metadatainformation can include, for example, parent-child relationships betweenmanaged objects (“MOs”) and clustered managed objects (“CMOs”), propertyinformation of a MO or CMO, and/or information about all events of anygiven MO or CMO. A more detailed description of the Agent MetadataService 304 will be provided below. The Agent Managed Object QueryService 305 is used by the Discovery Service 311 and providesinformation regarding all MO and CMO instances that have been created onthe agent 212. The information may include instance properties andproperties of some or all events under any instance. The Agent TrapRegistration Service 306 is a service used by the Discovery Service 311and can receive requests for addition, deletion and update of listenersinterested in receiving alert notifications that an agent 301 can send.The information used for registration can include parameters to identifythe listener uniquely, connection parameters, security credentials,and/or information on proxy servers, if present. The Discovery Service311, at the end of discovery, can register with the Agent TrapRegistration Service 306 to add itself as a listener.

The Discovery Service 311, Metadata Cache Service 307, Schema ManagerService 308, Profile Service 309, and Performance Data CollectionService 310 are examples of services running on the manager 207. TheDiscovery Service 311 is the main service that interacts with otherservices running on the manager 302 and can receive one or more targetsfor discovery. A target can be, for example, an agent, a MO, or a CMO.

The sequence of execution of operations on a specified target during thediscovery process will be described with respect to FIGS. 3 and 4. TheDiscovery Service 311 first retrieves metadata information from theMetadata Cache Service 307 (Step S401). The Metadata Cache Service 307can retrieve metadata information during discovery from the AgentMetadata Service 304 and the Schema Manager Service 308 and can cachethe information to speed up the discovery process. After retrieval ofmetadata information, the Discovery Service 311 finds all configured MOand CMO instances on the Agent Managed Object Query Service 305 (StepS402). Data pertaining to the discovered agents is then provided by theDiscovery Service 311 to be stored in a database repository through theSchema Manager Service 308 (Step S403). The Schema Manager Service 308can provide a facade over the database repository which can facilitateaddition/deletion/update of agent schema objects into the repository. Aspart of object creation, the Schema Manager Service 308 can call thePerformance Data Collection Service 310 to collect and analyzeperformance data from the agents, if required (Step S404). The DiscoveryService 311 can then register with the Agent Trap Registration Service306 in order to receive alert notifications from the agents (Step S405).

A Profile Service 309 can store the discovery target information asindividual discovery profiles, eliminating the need for continuouslyentering discovery details. A discovery profile may include of one ormore targets, allowing a user to create a logical grouping of discoverytargets. If a profile contains multiple targets, the profile can beeither a discrete list of targets or can be specified by a range ofInternet Protocol (IP) addresses. Apart from the host name, or IPaddresses, the discovery profile can also contain proxy information usedto connect to the host, the connection details, security credentials,and/or a flag indicating whether the profile has been enabled. TheProfile Service 309 can supply the Discovery Service 311 with a list ofstored profiles and upon request, can be used to create, update, ordelete the profiles. The Performance Data Collection Service 310 addsthe discovered agent objects for data collection.

The Discovery Wizard 312, and Discovery Monitor 313 are graphical userinterfaces 205 that interact with Discovery Service 311. The DiscoveryWizard 312 provides a user interface to describe the discovery targetsby pulling up the existing list of profiles from the Profile Service 309and displaying them to a user in a tabular format. The user can createnew discovery profiles, delete old ones, or update various targetfields. The Discovery Wizard 312 can also create a set of discretetarget objects from the current profiles and submit the list to theDiscovery Service 311. The Discovery Wizard 312 then launches theDiscovery Monitor 313, which is a user interface that keeps track of thestatus and results of the current discovery. The Discovery Monitor 313indicates to a user if a discovery process is running by continuouslypolling status and log messages from the Discovery Service 311 anddisplaying them to the user. When discovery is complete, the DiscoveryMonitor. 313 can display the results of discovery as a tree to the user.

The Agent MetaData Service 304 is a SOAP based service on the agent 301that is used by SOAP clients (e.g., manager 207) to get agent metadata.According to an embodiment of the present disclosure, the following arethe-data elements for the agent that the Agent Metadata Service 304 canprovide to all SOAP clients: Product Name, Product Version, Product Key,Application Server Name, Application Server Version, Build Number, AgentClass Name, Event Class Name, Alerts Class Name, Managed Objects,Managed Object Path, Managed Object Relations, Managed Object DescriptorProperties, Event Set, Event Set Descriptor Properties, Event List,Event Relations, etc. The following methods can be invoked by the AgentMetadata Service 304: “getabout” (can return Product Name, ProductVersion, Product Key, Application Server Name, Application ServerVersion, and Build Number); “getAgentCoreClasses” (can return AgentClass Name, Event Class Name, and Alerts Class Name); “getMOList” (canreturn a list of all managed objects); “getMORelations” (can return atree structure of all managed object relations);“getMODescriptorProperties” (can return managed object descriptorproperties, such as, Name, Nice Name, Description, and other userinterface related properties for a managed object); “getPropertySet”(can return a tree structure of managed objects with their properties);“getEventSetList” (can return a list of events for a managed object);“getEventSetDescriptorProperties” (can return managed object descriptorproperties, such as, Name, Nice Name, Description, and other userinterface related properties for an event set); “getEventList” (canreturn the list of events in an event set for a managed object);“getEventRelations” (can return a tree structure consisting of eventsets and the events for a managed object); “getEventPropertySet” (canreturn a tree structure consisting of event name as a node and eventproperty name values as attributes). FIG. 5 shows how the Agent MetadataService 304 provides metadata to SOAP clients (e.g., manager 207). TheAgent Metadata Service 304 queries an underlying Managed Object Layer501 which in turn retrieves data from an XML layer 502 to provide themetadata to the clients.

The Discovery Wizard 312 is the graphical user interface 205 thatenables a user to access the Discovery Service 311. There are fourdifferent common tasks that can be performed for discovery by a user,discovering an agent with valid agent host and agent port, discoveringan agent with valid agent host name and port, discovering multipleagents, and updating profiles, each of which will be described infurther detail below.

A user can discover an agent with a valid agent host and an agent port.According to an embodiment of the present disclosure, a user firstchooses one of two modes of operation. FIG. 6 illustrates a GUI allowingthe user to choose between the two different discovery modes. The firstmode (A) can walk a user through the process of adding a host step bystep. The user can then manipulate the list of targets. The second mode(B) can take a user directly to the advanced profile table, where theuser can immediately start manipulating the list of targets fordiscovery. FIG. 7 shows the second step of the discovery process, inwhich a GUI is provided allowing the user to select a user-friendly namefor the discovery profile and enter a profile description. FIG. 8illustrates a GUI allowing a user to perform the third step of enteringthe agent host information. Hosts can either be specified by name or byaddress. There are various ways of specifying multiple hosts. Forexample, a user can specify a comma-separated list of hosts andaddresses or specify an IP address range to discovery by checking the“use range” box. A fourth step in the discovery process involvesinputting the proxy details for either an agent or manager. FIG. 9illustrates a GUI allowing the user to input their information. If auser chooses to enter the agent proxy details, then the user canconfigure proxy options, if any, for a manager to reach the agent. If auser chooses to enter the manager proxy details, then the user canconfigure proxy options, if any, for the agent to reach the manager. Incase the proxy uses authentication, the user can also supply proxycredentials during this step. A fifth step in the discovery processinvolves inputting the connection details for either an agent ormanager. FIG. 10 illustrates a GUI allowing the user to input thisinformation. If a user chooses to enter the agent connection details,then the user can specify custom communication parameters to be used bythe manager in order to reach the agent. If the user chooses to enterthe manager connection details, then the user can specify customcommunication parameters to be used by the agent in order to reach themanager. For both of these options, the user can specify infinitetimeout by checking the requisite box. FIG. 11 illustrates a GUI forentering security credentials. A user can enter the read, write, andexecute security credentials on the agent for use by the manager in thediscovery and its subsequent interaction with the agent. Various agentinterfaces are exposed at various security levels and these credentialscan help in providing access control on the agent side. The last stepincludes displaying a list of discovered agents to a user. The list cancontain the agent host entered by the user. FIG. 12 illustrates a GUIused for presenting the information to the user.

A user can discover an agent with a valid agent host name and an agentport. This task is similar to the previous task, except that the userchooses the second mode (advanced profile table) in the first step anddoes not have to enter profile information.

A user can discover multiple agents by following the above steps andentering in multiple hosts and ports for the sixth step. To specifymultiple hosts, a user can type a comma separated list of machine namesfor hosts or select the address range check box and specify the range ofIP address that are to be discovered. To specify multiple ports, a usercan either enter a comma separated list of ports (agent will bediscovered using each port number present in the list), specify a rangeof ports (agent will be discovered using each port number present in therange), or can specify a single port (all agents will be discoveredusing same port number). All the hosts specified by a user can bedisplayed in a tabular format. The user can select a particular agent byselecting the row for that agent. The corresponding detailed view forthe agent can be shown at the bottom of the selected row.

According to an embodiment of the present disclosure, an agent can be apure Java implementation. An agent can create and monitor real timetransactions and synthetic non-intrusive business logic transactions,where the business logic can include object support. An agent canautomatically load static and dynamic classes of the application serverand can persistently store data. For each metric, an agent can acceptuser-defined policies, via a user interface to escalate a state(available states can include normal, warning, or critical). When astate is changed within the agent, the agent can send atrap/notification to all its registered managers. A trap/notification isa message sent from an agent to notify another system or alert a managerof changes or events that occur on the agent system. Thesetraps/notifications can be sent using SOAP. According to an embodimentof the present disclosure, an agent can run as a standard windowsservice and allow a user to execute task/scripts on the server.

An agent can also monitor J2EE applications, operating system resources,generic applications, etc. Managed objects are provided for each ofthese features and are each described in detail below.

Managed Objects For Monitoring J2EE Applications

1) Administration Server Managed Object

An Administration Server Managed Object can monitor “Access” where theagent sends a “ping” to the administration server to determine if theserver is accessible. The Administration Server Managed Object can alsomonitor the “Most Recent Symptom” found in a log file and the “LogMessage Broadcast Rate”, which is the rate per minute at which logmessages are being broadcast.

2) Cluster Managed Object

A Cluster Managed Object can monitor the following events: “FragmentsSent” (total number of multicast fragments sent from the server into thecluster), “Fragments Sent Rate”(total number of multicast fragments sentfrom the server into the cluster per minute), “Fragments Received”(total number of multicast messages received on the server from thecluster), “Fragments Received Rate” (total number of multicast messagesreceived on the server from the cluster per minute), “Multicast MessagesLost” (total number of incoming multicast messages that were lostaccording to the server), “Multicast Messages Lost Rate”(total number ofincoming multicast messages that were lost according to the server perminute), “Foreign Fragments Dropped” (number of fragments thatoriginated in foreign domains/cluster that use the same multicastaddress), “Foreign Fragments Dropped Rate”(number of fragments thatoriginated in foreign domains/cluster that use the same multicastaddress per minute), “Alive Server” (current total number of aliveservers in the cluster), “Resend Requests” (number of state-deltamessages that had to be resent because a receiving server in the clustermissed a message), and “# of Primaries” (number of objects that thelocal server hosts as primaries).

3) Managed Server Managed Object

A Managed Server Managed Object can include the following children: aConnection Managed Server Child Managed Object, an Execute Queue ManagedServer Child Managed Object, a Thread Managed Server Child ManagedObject, each of which will be described in further detail below.

The Managed Server Managed Object can monitor “Access” where the agentsends a “ping” to the administration server to determine if the serveris available. The Managed Server Managed Object can also monitor the“Most Recent Symptom” found in a log file and the “Log Message BroadcastRate”, which is the rate per minute at which log messages are beingbroadcast. The following events can also be supervised by the ManagedServer Managed Object: “Heap Size Free” (current heap free), “Heap SizeUsed” (current size of the heap), “Heap Usage Rate” (heap usage perminute), “Login Attempts While Locked”(cumulative number of invalidlogins attempted on the server while the user was locked), “UserLockout” (cumulative number of user lockouts done on the server), “UserLockout Rate” (cumulative number of user lockouts done on the server perminute), “Unlocked Users”(the number of times a user has been unlockedon the server), “Invalid Login Attempts”(cumulative number of invalidlogins attempted on the server), “Invalid Login Attempts Rate”(cumulative number of invalid logins attempted on the server perminute), “Invalid Login Users—High” (highwater number of users withoutstanding invalid login attempts for the server), “Current LockedUsers” (number of currently locked users on the server), “Current LockedUsers Rate” (number of currently locked users on the server per minute),Sockets Opened (“total number of sockets opened”), “Sockets Opened Rate”(total number of sockets opened per minute), “Restarts” (total number ofrestarts), “Current Open Sockets”(current number of open sockets),“Current Connections” (current number of connections to the server),“Maximum Connections” (peak number of connections to the server sincethe last reset), “Total Connections” (total number of connections madeto the server since the last reset), “Total Connections Rate” (totalnumber of connections per minute made to the server since the lastreset), “Current JMS Servers” (current number of Java Message Servers(JMS) that are deployed on the server instance), “Maximum JMS Servers”(peak number of JMS servers that were deployed on the server instancesince the server was started), “Total JMS Servers” (number of JMSservers that were deployed on the server instance since the server wasstarted), “Transactions Rolled Back” (number of transactions that wererolled back), “Transactions Rolled Back Rate” (number of transactionsper minute that were rolled back), “Transactions With Heuristics StatusRate” (number of transactions per minute that completed with a heuristicstatus), “Transactions Rolled Back Due To System Error”(number oftransactions that were rolled back due to an internal system error),“Transactions Rolled Back Due To System Error Rate” (number oftransactions per minute that were rolled back due to an internal systemerror), “Transactions Rolled Back Due To Application Error”(number oftransactions that were rolled back due to an application error),“Transactions Rolled Back Due To Application ErrorRate”(number-of-transactions per minute that were rolled back due to anapplication error), “Abandoned Transactions” (number of transactionsthat were abandoned), “Abandoned Transactions Rate” (number oftransactions per minute that were abandoned), “Total Transactions”(total number of transactions processed, including all committed androlled back and heuristic transaction completions), “Total TransactionsRate” (total number of transactions per minute processed, including allcommitted and rolled back and heuristic transaction completions),“Transactions Rolled Back Due To Timeout” (number of transactions thatwere rolled back due to a timeout expiration), “Transactions Rolled BackDue To Timeout Rate” (number of transactions per minute that were rolledback due to a timeout expiration), “Active Transactions” (number ofactive transactions on the server), “Active Transactions Rate” (numberof active transactions per minute on the server), “TransactionsCommitted” (number of committed transactions), “Transactions CommittedRate” (number of committed transactions per minute), “TransactionsRolled Back Due To Resource Error” (number of transactions that wererolled back due to a resource error), and “Transactions Rolled Back Dueto Resource Error Rate”(number of transactions per minute that wererolled back due to a resource error).

a) Connection—Managed Server Child Managed Object

This Child Managed Object can monitor the following connection events:“Bytes Received Rate” (number of bytes received per minute since thelast reset), “Bytes Sent Rate”(number of bytes sent per minute since thelast reset), “Messages Received” (number of messages received by theuser since the last reset), “Messages Received Rate” (number of messagesreceived per minute by the user since the last reset), “Messages Sent”(number of messages sent by the session since the last reset), and“Messages Sent Rate” (number of messages sent per minute by the sessionsince the last reset).

b) Execute Queue—Managed Server Child Managed Object

This Child Managed Object can monitor the following performance events:“Pending Requests” (number of waiting requests in the queue), “ServicedRequest Total”(number of requests which have been processed by thequeue), “Throughput” (number of requests per minute which have beenprocessed by the queue), “Idle Execute Thread” (number of idle threadsassigned to the queue), and “Maximum Pending Request Time” (time thatthe longest waiting request was placed in the queue).

c) Thread—Managed Server Child Managed Object

This Child Managed Object can monitor the following events: “TotalService Requests” (number of requests which have been processed by thequeue), and “Throughput”(number of requests per minute which have beenprocessed by the queue).

4) Servlet Managed Object

A Servlet Managed Object can monitor the following events: “Access”(test to determine whether a particular EJB is available), “TotalReloads” (total number of reloads of the servlet), “Average ExecutionTime” (average amount of time all invocations of the servlet have beenexecuted since created), “Maximum Execution Time” (amount of time thesingle shortest invocation of the servlet has executed since created),“Minimum Execution Time” (amount of time the single longest invocationof the servlet has executed since created), “Invocation Total” (totalnumber of invocations of the servlet), and “Invocation Total Rate”(total number of invocations of the servlet per minute).

5) EJB Managed Object

An EJB Managed Object can monitor the following events: “Access” (testto determine whether a particular EJB is available), “TransactionsRolled Back” (total transactions rolled back), “Transactions Rolled BackRate” (total transactions rolled back per minute), “Transactions TimedOut” (total transactions timed out), “Transactions Timed Out Rate”(total transactions timed out per minute), “Transactions Committed”(total transactions committed), and “Transactions Committed Rate” (totaltransactions committed per minute).

6) Entity EJB Managed Object

An Entity EJB Managed Object can monitor the following events: “CacheAccess” (cache access count), “Cache Access Rate” (cache access countper minute), “Cached Beans Rate” (number of beans currently in cache),“Cache Hit Rate” (cache hit count), “Activation”(number of times thebean instance was activated), “Activation Rate” (number of times thebean instance was activated per minute), “Passivation” (number of timesthe bean instance was passivated), “Passivation Rate” (number of timesthe bean instance was passivated per minute), “Current Lock Entries”,“Total Waiters”, “Total Waiter Rate”, “Lock Manager Access”, “TotalTimeout”, “Transactions Rolled Back” (total transactions rolled back),“Transactions Rolled Back Rate” (total transactions rolled back perminute), “Transactions Timed Out” (total transactions rolled back perminute), “Transactions Timed Out Rate” (total transactions timed out perminute), “Transactions Committed” (total transactions committed),“Transactions Committed Rate” (total transactions committed per minute),“Total Timeout” (timeout total count), “Beans In Use” (number of beansin use), “Idle Beans” (number of idle beans), and “Waiter Total” (totalwaiter count).

7) Stateful EJB Managed Object

A Stateful EJB Managed Object can monitor the following events: “CacheAccess” (cache access count), “Cache Access Rate” (cache access countper minute), “Cached Beans Rate” (number of beans currently in cache),“Cache Hit Rate” (cache hit count), “Activation” (number of times thebean instance was activated), “Activation Rate” (number of times thebean instance was activated per minute), “Passivation” (number of timesthe bean instance was passivated), “Passivation Rate” (number of timesthe bean instance was passivated per minute), “Current Lock Entries”,“Total Waiters”, “Total Waiter Rate”, “Lock Manager Access”, “TotalTimeout”, “Transactions Rolled Back” (total transactions rolled back),“Transactions Rolled Back Rate” (total transactions rolled back perminute), “Transactions Timed Out” (total transactions rolled back perminute), “Transactions Timed Out Rate” (total transactions timed out perminute), “Transactions Committed” (total transactions committed), and“Transactions Committed Rate” (total transactions committed per minute).

8) Stateless EJB Managed Object

A Stateless EJB Managed Object can monitor the following events:“Transactions Rolled Back” (total transactions rolled back),“Transactions Rolled Back Rate” (total transactions rolled back perminute), “Transactions Timed Out” (total transactions timed out),“Transactions Timed Out Rate” (total transactions timed out per minute),“Transactions Committed” (total transactions committed), “TransactionsCommitted Rate” (total transactions committed per minute), “TotalTimeout” (timeout total count), “Beans In Use” (number of beans in use),“Idle Beans” (number of idle beans), and “Waiter Total” (total waitercount).

9) Message EJB Managed Object

A Message EJB Managed Object can monitor the following events:“Transactions Rolled Back” (total transactions rolled back),“Transactions Rolled Back Rate” (total transactions rolled back perminute), “Transactions Timed Out” (total transactions timed out),“Transactions Timed Out Rate” (total transactions timed out per minute),“Transactions Committed” (total transactions committed), “TransactionsCommitted Rate” (total transactions committed per minute), “TotalTimeout” (timeout total count), “Beans In Use” (number of beans in use),“Idle Beans” (number of idle beans), and “Waiter Total” (total waitercount).

10) JDBC Managed Object

A JDBC Managed Object can monitor the following events: “Access” (testto determine whether the EJB is available), “Active Connections”(current total number of active connections), “Active Connections Rate”(current total number of active connections per minute), “TotalConnections” (total number of JDBC connections since the pool isinstantiated), “Total Connections Rate” (total number of JDBCconnections per minute since the pool is instantiated), “ConnectionDelay Time” (average time necessary to get a connection from thedatabase), “Waiting For Connection” (current total number waiting for aconnection), “Maximum Waiting For Connection” (the high water mark ofwaiters for a connection), “Failure To Reconnect” (number of cases whena connection pool attempted to refresh a connection to a database andfailed), “Failures To Reconnect Rate” (number of cases when a connectionpool attempted to refresh a connection to a database and failed perminute), “Maximum Wait In Seconds” (number of seconds the longest waiterfor a connection waited), “Leaked Connection” (number of leakedconnections), “Leaked Connection Rate” (number of leaked connections perminute), “Prep Statement Cache Miss”, and “Prep Statement Cache Hit”.

11) Connector Connections Managed Object

A Connector Connections Managed Object can include a ConnectorConnection Child Managed Object, which will be described in furtherdetail below.

The Connector Connections Managed Object can monitor the followingevents: “Current Connection” (current total active connections),“Maximum Active Connections” (high water mark of active connections inthe Connector Pool since the pool was first instantiated), “AverageUsage” (running average usage of created connections that are active inthe Connector Pool since the pool was last shrunk), “Total Created”(total number of connector connections created in the Connector Poolsince the pool was instantiated), “Total Destroyed Connections” (totalnumber of connector connections destroyed in the Connector Pool sincethe pool was instantiated), “Total Matched Connections” (total number oftimes a request for a Connector connections was satisfied via the use ofan existing created connection since the pool was instantiated), “TotalRejected Connections” (total number of rejected requests for a Connectorconnections in the Connector Pool since the pool was instantiated),“Current Connections Free” (current total free connections), “MaximumConnections Free” (high water mark of free connections in the ConnectorPool since the pool was instantiated), “Initial Capacity” (initialcapacity configured for the Connector connection pool), “MaximumCapacity” (maximum capacity configured for the Connector connectionpool), “Total Recycled Connections” (total number of Connectorconnections that have been recycled in the Connector Pool since the poolwas instantiated), “Shrink Count Down” (amount of time left (in minutes)until an attempt to shrink the pool will be made), and “Shrink Period”(the amount of time (in minutes) of the Connector connection pool).

a) Connector—Connector Connection Child Managed Object

This Child Managed Object can monitor the following connection events:“Active Connection Handles” (current total active connection handles forthe connection), “Maximum Active Connection Handles” (high water mark ofactive connection handles for the connection since the connection wascreated), and “Total Connection Handles Created” (total number ofconnection handles created for the connection since the connection wascreated).

12) Jolt Connections Managed Object

A Jolt Connection Managed Object can include a Jolt Connection ChildManaged Object, which will be described in further detail below.

The Jolt Connection Managed Object can monitor the following event:“Maximum Capacity” (maximum capacity configured for the Connectorconnection pool).

a) Connection—Jolt Connector Managed Object

This Child Managed Object can monitor the following connection events:“Error Requests” (current total active connection handles for theconnection), “Pending Requests” (pending request count), and “RequestCount” (total request count).

13) WLEC Connector Managed Object

A WLEC Connector Managed Object can include a WLEC Connector ChildManaged Object, which will be described in further detail below.

The WLEC Connector Managed Object can monitor the following event:“Maximum Capacity” (maximum capacity configured for the Connectorconnection pool).

a) Connection—WLEC Connector Managed Object

This Child Managed Object can monitor the following connection events:“Error Requests” (current total active connection handles for theconnection), “Pending Requests” (pending request count), and “RequestCount” (total request count).

14) Business Logic Managed Object

A Business Logic Managed Object monitors a Content monitor for allserver versions.

15) Insider Managed Object

An Insider Managed Object monitors the real-time performance of EJBs,servlets, and JDBCs.

Managed Objects For Monitoring Operating System Resources

1) Operating System Resources Managed Object

An Operating System Resources Managed Object can include a CPUUser—Operating System Resources Child Managed Object and a FileSystem—Operating System Resources Child Managed Object, each of whichwill be described in further detail below.

The Operating System Resources Managed Object can monitor the followingevents: “Available Memory” (real value of available memory), “AvailableMemory Percent”(percentage value of available memory), “Free Memory”(real value of free memory), “Free Memory Percent” (percentage value offree memory), “Swap Space In Use” (swap space that is currently in use),“Free Swap Space” (swap space that is currently free), and “Paging”.

a) CPU User—Operating System Resources Child Managed Object

This Child Managed Object can monitor the following CPU User events:“CPU Used” (percentage of CPU used), “Idle Time” (percentage of idletime), “Wait Time” (percentage of wait time), “System Time” (percentageof system time), and “User Time” (percentage of user time).

b) File System—Operating System Resources Child Managed Object

This Child Managed Object can monitor the following File System events:“Available Disk Space” (currently available disk space), “Available DiskSpace Percent” (percentage of currently available disk space), “FileSize” (total file size), and “File Size Used” (percentage of file sizebeing utilized.

Managed Objects For Monitoring Generic Applications

1) URL Monitor Managed Object

A URL Monitor Managed Object can include a File System—Operating SystemResources Child Managed Object, which will be described in furtherdetail below.

The URL Monitor Managed Object can monitor the following events: “URLStatus” (test to check whether URL is accessible), “Content Match”(enter a string of text to check for in the returned page or frameset),“Document Checksum” (a checksum comparison each subsequent time itruns), “Round Trip Time” (total time for the entire request), “DNSLookup Time” (amount of time to translate the host name to an IPaddress), “Connect Time” (amount of time to make the connection),“Response Time” (amount of time before the first response was received),“Download Time” (amount of time to receive the page contents), and “Age”(amount of time between the current time and the last modified time forthe page).

a) File System—Operating System Resources Child Managed Object

This Child Managed Object can monitor the following File System events:“Available Disk Space” (currently available disk space), “Available DiskSpace Percent” (percentage of currently available disk space), “FileSize” (total file size), and “File Size Used” (percentage of file sizebeing utilized.

2) Port Monitor Managed Object

A Port Monitor Managed Object can monitor the following events: “Access”(test to check whether the port is accessible or not), and “Time” (timetaken to connect to the port).

3) Process Monitor Managed Object

A Process Monitor Managed Object can monitor the following events:“Process Size” (real value of the size of the process), “Memory Ratio”(ratio of actual size of the memory occupied by the process to thephysical memory on the machine expressed as a percentage), “Number ofThreads” (number of threads associated with the process), and “PercentCPU Used” (percent value of the CPU used by the process).

4) HTTP Server Managed Object

A HTTP Server Managed Object only monitors the access event for theserver.

5) Custom Application Managed Object

A Custom Application Managed Object can monitor the TCP Server and logfiles access events for the server.

The specific embodiments described herein are illustrative, and manyvariations can be introduced on these embodiments without departing fromthe spirit of the disclosure or from the scope of the appended claims.Elements and/or features of different illustrative embodiments may becombined with each other and/or substituted for each other within thescope of this disclosure and appended claims.

Numerous additional modifications and variations of the presentdisclosure are possible in view of the above-teachings. It is thereforeto be understood that within the scope of the appended claims, thepresent disclosure may be practiced other than as specifically describedherein.

1. A method of alert notification, comprising: sending a Simple ObjectAccess Protocol (SOAP) based alert notification from one or more agents;and receiving the SOAP based alert notifications at a manager.
 2. Themethod of claim 1, wherein the SOAP based alert notification is sent toa manager by one or more agents at a predefined interval.
 3. The methodof claim 1, wherein the SOAP based alert notifications alert the managerof changes that occur on one or more agents.
 4. The method of claim 1,wherein a discovery service registers a manager with an agent trapregistration service to receive the SOAP based alert notifications fromone or more agents.
 5. The method of claim 4, wherein the agent trapregistration service resides on one or more agents.
 6. The method ofclaim 4, wherein the agent trap notification service requiresregistration information from the manager, wherein the registrationinformation comprises the manager parameters, connection parameters,security credentials, and/or proxy server information.
 7. The method ofclaim 4, wherein the agent trap notification service receives requestsfor the addition, deletion, and update of managers interested inreceiving the SOAP based alert notifications.
 8. A system of alertnotification, comprising: at least one agent for sending a SOAP basedalert notification; and at least one manager for receiving the SOAPbased alert notification.
 9. The system of claim 8, wherein the SOAPbased alert notification is sent to a manager by one or more agents at apredefined interval.
 10. The system of claim 8, wherein the SOAP basedalert notifications alert the manager of changes that occur on one ormore agents.
 11. The system of claim 8, wherein a discovery serviceregisters a manager with an agent trap registration service to receivethe SOAP based alert notifications from one or more agents.
 12. Thesystem of claim 11, wherein the agent trap registration service resideson one or more agents.
 13. The system of claim 11, wherein the agenttrap notification service requires registration information from themanager, wherein the registration information comprises the managerparameters, connection parameters, security credentials, and/or proxyserver information.
 14. The system of claim 11, wherein the agent trapnotification service receives requests for the addition, deletion, andupdate of managers interested in receiving the SOAP based alertnotifications.
 15. A computer readable storage medium including computerexecutable code for alert notification, comprising: code for sending aSOAP based alert notification; and code for receiving the SOAP basedalert notification.
 16. The computer readable storage medium of claim15, wherein the SOAP based alert notification is sent to a manager byone or more agents at a predefined interval.
 17. The computer readablestorage medium of claim 15, wherein the SOAP based alert notificationsalert the manager of changes that occur on one or more agents.
 18. Thecomputer readable storage medium of claim 15, wherein a discoveryservice registers a manager with an agent trap registration service toreceive the SOAP based alert notifications from one or more agents. 19.The computer readable storage medium of claim 18, wherein the agent trapregistration service resides on one or more agents.
 20. The computerreadable storage medium of claim 18, wherein the agent trap notificationservice requires registration information from the manager, wherein theregistration information comprises the manager parameters, connectionparameters, security credentials, and/or proxy server information. 21.The computer readable storage medium of claim 18, wherein the agent trapnotification service receives requests for the addition, deletion, andupdate of managers interested in receiving the SOAP based alertnotifications.